Skip to content

Synchronise 2025.1 with upstream#213

Open
github-actions[bot] wants to merge 2 commits into
stackhpc/2025.1from
upstream/2025.1-2026-06-15
Open

Synchronise 2025.1 with upstream#213
github-actions[bot] wants to merge 2 commits into
stackhpc/2025.1from
upstream/2025.1-2026-06-15

Conversation

@github-actions

Copy link
Copy Markdown

This PR contains a snapshot of 2025.1 from upstream stable/2025.1.

kk7ds and others added 2 commits May 11, 2026 10:21
As noted in the referenced bug, we were previously not passing the
user's context during a resize operation when looking up the target
flavor. This means we end up using an admin context, which can find
any flavor, including private ones we should not be able to see thus
allowing resize to another project's private flavor. Simply passing
the context to the lookup does the needed filtering.

Assisted-By: Claude Opus 4.6
Closes-Bug: #2151256
Change-Id: I469688be203c319dd048d6a99057b8d98369de0e
Signed-off-by: Dan Smith <dansmith@redhat.com>
(cherry picked from commit ef7ddda)
(cherry picked from commit 36dd74f)
(cherry picked from commit 07deedd)
@github-actions github-actions Bot requested a review from a team as a code owner June 15, 2026 08:27
@github-actions github-actions Bot added automated Automated action performed by GitHub Actions synchronisation labels Jun 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated action performed by GitHub Actions synchronisation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant